Remove /dev bind mount from example#110
Conversation
There is no need to bind-mount /dev when the container is privileged, the container runtime provides everything in /dev that Gluster expects.
|
See-also: gluster/gluster-kubernetes#538 |
|
I wonder if there are obscure or old runtimes that did not mount /dev automatically for a privleged container. If that's the case perhaps we could add a line to the containers start scripts to refuse to run if it fails to find a populated /dev. |
|
@SaravanaStorageNetwork @nixpanic Do you guys have any document ( may be from docker itself ?) which kind of explain the behaviour with |
|
Unfortunately there does not seem to be a clear description of what
'privileged' really includes. There are differences between Docker and
CRI-O features, but I have not found any documentation about
'privileged' in either project.
|
|
Does it make sense to reach out to the crio project and ask for more detailed descriptions of this behavior? Does that project have a mailing list or maybe we should just create an issue at the cri-o github project? I'd be happy to help if need be. |
|
Closing as stale. |
4 participants
There is no need to bind-mount /dev when the container is privileged,
the container runtime provides everything in /dev that Gluster expects.
Fixes: https://bugzilla.redhat.com/1651270